Method for establishing a secure private interconnection over a multipath network

ABSTRACT

A method for establishing a fully private, information theoretically secure interconnection between a source and a destination, over an unmanaged data network with at least a portion of a public infrastructure. Accordingly, n shares of the source data are created at the source according to a predetermined secret sharing scheme and the shares are sent to the data network, while encrypting the sent data using (n,k) secret sharing. A plurality of intermediating nodes are deployed in different locations over the network, to create a plurality of fully and/or partially independent paths in different directions on the path from the source to the destination, and with sufficient data separation. Then, the shares are sent over the plurality of fully and/or partially independent paths while forcing shares&#39; carrying packets to pass through selected intermediate nodes, such that no router at any intermediating nodes intercepts k or more shares.

FIELD OF THE INVENTION

The present invention relates to the field of communication networks,such as the Internet. More specifically, the present invention isrelated to a secret sharing scheme, which is particularly effective forestablishing a private channel for two parties communicating overmultipath communication over hybrid infrastructures including clouds,servers in Points of Present (PoPs) and backup communication channels.The secret sharing scheme may use fused public directoriesauthentication to replace the secrecy and authenticity provided by thepublic key infrastructure, for eliminating the need for trustedauthority and protection of keys.

BACKGROUND OF THE INVENTION

Public key infrastructure is based on modern cryptography, where theexistence of one-way-functions is assumed and such speculated to beone-way-functions are used in practice. The security is based oncomputational security, rather than the classical informationtheoretical secure techniques, such as the one-time-pad (a randomcollection of letters each used at most once to encrypt messages withcomplete security) that implies unconditional secrecy, in particular,cannot be broken by extensive computation for revealing keys. Beyond thecomputational security promise, there is a need to avoidman-in-the-middle attacks by authenticating the parties using a trustedauthority that authenticates the user and stores keys. In turn, theexistence of keys is a target for attacks.

A Virtual Private Network (VPN—a network that uses a publicinfrastructure, such as the Internet, to provide secure access andensured privacy through security procedures and tunneling protocols)provides easy access from the cloud into a corporate network and itsinternal resources. However, the encryption protocols that are usedtoday for establishing a VPN are based on encryption keys (PKI—publickey infrastructure). In order to create a secure channel between twoentities, the destination must provide the sender a certification of itspublic key, signed by a trusted Certification Authority (CA). If thesender trusts the certification, the sender uses the public key of theCA to reveal the destination public key and a secure session begins.However, if an intruder steals identification of some entity andprovides a certified key to the client, the client may use theintruder's key to encrypt the data (e.g., man-in-the-middle attackMITM). Therefore, one of the vulnerabilities of using PKI is identityspoofing that causes the source to use the attacker's key.

Another limitation of existing VPNs is the fact that they are based oncomputational secured protocols, i.e., with enough computational power,an intruder can reveal the encrypted data. Since the computational powerof machines continuously grows over the years, the length of theencryption key must increase in order to maintain the desired level ofsecurity. However, increasing the length of the key implies degradationin the performance of the encryption process. In addition, there aremany existing hardware devices that do not support this new length ofthe keys and therefore, there are cases where the encryption isvulnerable at a portion of the channel. Also, there are many attacksfrom the last few years that succeed to break these protocols evenwithout having the key, such as, the Padding Oracle On Downgraded LegacyEncryption (POODLE) attack, (which is a man-in-the-middle exploit), or“Compression Ratio Info-leak Made Easy” (CRIME) attack, (which is asecurity exploit against secret web cookies). Moreover, unlikeinformation theoretical secure based protocol, the computational securedprotocol is not everlasting and basically, it is just a matter of timefor the information to be revealed. As a result of the abovelimitations, an attacker can sniff the data anywhere in network (in theimmediate perimeter, in the close zone e.g., a country, or in thebackbone—between countries) and then, or at any time in the future, tryto break the encryption.

Cloud computing (a form of distributed computing accessed through thenetwork, with the ability to run a program on many connected computersat the same time) is one of the fastest growing opportunities forenterprises and service providers. Enterprises use theInfrastructure-as-a-Service model (IaaS model—a form of cloud computingthat provides virtualized computing resources over the Internet), tobuild private and public clouds that reduce operating costs and increasethe reliability of their critical information systems.

One of the existing solutions is CloudBridge technology presented byCitrix R® Systems, Inc. (Fort Lauderdale, Fla., U.S.A.), which providesa unified platform that accelerates applications across public andprivate networks, resulting in superior application performance and enduser experience. CloudBridge connects across third-party public cloudand private networks, thereby offering a platform for cloud-enablingthird-party applications. However, the privacy of CloudBridge isachieved using a standard VPN, and therefore, is limited to acomputational secured channel.

Secret-sharing is a tool used in many cryptographic protocols. Asecret-sharing scheme involves a dealer who has a secret, a set of nparties, and a collection of subsets of k parties. According to asecret-sharing scheme, the dealer distributes shares to the parties suchthat any subset of k parties can reconstruct the secret from its shares,and any subset with less than k parties cannot reveal any partialinformation on the secret. Secret-sharing schemes have numerousapplications in cryptography and distributed computing including secureinformation storage, secure multiparty computations, access control andmore. However, none of these schemes solve the problem of providinginformation theoretically secure source-destination communication overseveral optional paths.

Other prior art solutions deal with security issues that arise whenusing SDN, such as using secure multiparty computation techniques tosecure the data in the controller. Another prior art method focuses onthe effects of end-to-end encrypted networks on Network IntrusionDetection Systems (NIDS) operations. All data traffic sent to a receiverby a sender must be replicated and forwarded also to a Central IDS(CIDS), i.e., the sender sends the packet to a proxy and the proxyforwards it to the receiver as well as to the CIDS. Each connection issecured by VPN but thus unauthorized network sniffing is prevented.However, proxies are still able to access network packets relayedthrough them, which may expose the network packets to unwanted scrutiny.In order to ensure confidentiality with respect to the proxies,secret-sharing is used, such that the sender splits the packet to nshares and sends the shares to n proxies, the proxies further send theshares to the receiver and the CIDS. However, since VPN routes may crosscommon network components, the security of the prior art suggestedscheme is essentially identical to the security of VPN.

“SPREAD: Improving Network Security by Multipath Routing” (Lou et al.,Military Communications Conference, MILCOM '03, 2003 IEEE, Vol. 2)discloses an end-to-end multipath secure data delivery scheme, secureprotocol for reliable data delivery (SPREAD), as a complementarymechanism for the data confidentiality service in the public networks.The confidentiality is improved by forcing the secret sharing principlein the network via multipath routing. With a (T,N) secret sharingscheme, the message to be protected can be divided into N shares suchthat from any T or more shares, it can easily recover the message, whilefrom any T−1 or less shares, it should be impossible to recover themessage. Then the shares are delivered across the network via multipleindependent paths. The destination node reconstructs the originalmessage upon receiving T or more shares.

“MULTIPATH ROUTING APPROACH FOR SECURE DATA DELIVERY” (Lou et al.,Military Communications Conference, MILCOM '01, 2001 IEEE, Vol. 2)discloses an approach to enhance data confidentiality when transmittingacross insecure networks by taking advantage of the distributed natureof networks such as Internet or wireless networks and combine the secretsharing scheme and multipath routing. With a (T,N) secret sharingscheme, the secure message is divided into N shares such that themessage can be easily recovered from any T or more shares, while fromany T−1 or less shares, it is computationally impossible to recover themessage. Then, the shares are delivered across the network via Ndifferent paths using the multipath routing algorithm, where no T ormore paths can share a single node. The destination node can reconstructthe original message upon receiving T or more shares. Any intermediatenode does not intercept T shares necessary for the message recovery. Thealgorithm takes path independence, path quantity, as well as path costinto consideration and is able to find sets of node disjoint pathsbetween any source-destination pair.

However, both solutions proposed by Lou et al are not highly performanceefficient, since shares must be routed in predetermined totallyindependent source-to-destination paths, without considering the varyingdata traffic congestion/restrictions in each node. Therefore, in orderto obtain the desired level of security, the performance of packetdelivery may be compromised. In addition, there are situations whereaccording to the solutions proposed by Lou et al, it will be impossibleto find totally independent source-to-destination paths, while there isan existing solution, in which less than k shares traverse each node inthe network. For example, when each of the nodes A and B that areconnected to C forward (k−1)/2 of the arriving shares to C, while theirother (k−1)/2 are forwarded in different paths and some are merged inother nodes later, resulting in non-independent paths that still fulfillthe k−1 restriction.

It is therefore an object of the present invention, to provide animproved and secure VPN solution which is based on data separationscheme that overcomes the security vulnerabilities of the existing VPNs.

It is still an object of the present invention to provide a dataseparation scheme, for establishing private interconnection between asender and a receiver, without the need to use encryption keys ortrusted third party authorities for achieving security and privacy.

It is another object of the present invention to provide a dataseparation scheme, which is particularly effective for establishing aprivate channel, in which the information is information theoreticallysecure and is not bounded by the security of the VPN used.

It is a further object of the present invention to provide a dataseparation scheme for establishing a private channel in communicationnetworks, in which the transmitted information cannot be revealed,unless at least k shares are revealed.

It is yet another object of the present invention to provide a dataseparation scheme, particularly effective for establishing a privatechannel in the network, which does not require using a CertificationAuthority for identification to encrypt data communicated between twoparties over a data network, even if the data network exploits theinternet, public clouds and untrusted channels.

Other objects advantages of the present invention will become clear asthe description proceeds.

SUMMARY OF THE INVENTION

The present invention is directed to a method for establishing a fullyprivate, information theoretically secure interconnection between asource and a destination over an unmanaged data network having at leasta portion of a public infrastructure. Accordingly, n shares of thesource data are created at the source according to a predeterminedsecret sharing scheme and the shares are sent to the data network, whileencrypting the sent data using (n,k) secret sharing. A plurality ofintermediating nodes are deployed in different locations over thenetwork, to create a plurality of fully and/or partially independentpaths in different directions on the path from the source to thedestination, and with sufficient data separation. Then, the shares aresent over the plurality of fully and/or partially independent pathswhile forcing shares' carrying packets to pass through selectedintermediate nodes, such that no router at any intermediating nodesintercepts k or more shares.

The intermediating nodes may include one or more of the following:

Points of Presence (PoPs);

Computational clouds having a dedicated process for forcing shares'carrying packets to pass through selected intermediate nodes, accordingto a desired routing scheme;

Backup channels and paths.

The portion of the public infrastructure may include alternative pathssupplied by the same/different network/Internet providers.

The separation between tunnels belonging to fully and/or partiallyindependent paths may be made by encapsulation of the shares' packetsaccording to a routing scheme that creates at least partiallyindependent routing paths from source to destination, such that no nodealong a tunnel intercepts k or more shares.

During encapsulation, the header of each share-carrying packet may bechanged to a modified header, for forcing the shares' carrying packetsto pass through selected nodes, where each packet is forced to pass apossible different subset of selected nodes.

Public clouds deployed over the network may be used as nodes, byembedding a dedicated agent into a plurality of them, such that themodified header (which may be a part of the payload) will determine thenext intermediate destination which will be the node that has beenelected while creating each modified header.

Whenever the data network has a known topology, the flow may be testedoffline, to obtain the distribution of data through different nodes anddeploy the dedicated agents accordingly, to create the optimal routingpaths.

Whenever the data network has unknown topology a path/topology, recoverytools may be used to obtain the expected distribution of data throughdifferent nodes and verify, before sending the share carrying packets.

The path/topology recovery tools may be HP-OpenView, Freenats,Traceroute, TraceMAC or Batctl.

Sufficient data separation may be obtained by dynamically allocatingnodes, through which the share carrying packets will pass.

The inherent additional header of IPv6 may be used for creating tunnelsbetween IPv6 nodes, where data between nodes is sent over IPv4 protocollinks.

It is possible to encrypt the destination IP address, along with thepayload data, by creating n shares from the IP address of thedestination and sending the shares via several different paths betweenpairs of neighboring intermediate nodes, such that the header data isdecrypted at each intermediate nodes only by having at least k shares,and any subset of less than k shares cannot be used to decrypt theheader data.

Secret shared packets of different length may be created by padding theafter secret shared packets with random string of varying lengths, toavoid correlation of packets by a coalition of eavesdroppers. Some ofthe secret shared packets may be delayed to avoid time correlation.

Data packets may be encrypted by creating a one-time-pad in thebackground at the sender side; sending the created one-time-pad to thedestination over several paths; performing a bitwise XOR operationbetween the payload data and the bit string of the common one-time-pad;and sending the resulting bits of encrypted payload data over possibly asingle channel.

The present invention is also directed to a method for establishing afully private, information theoretically secure interconnection betweena source and a destination over a managed data network having at least aportion of a public infrastructure, comprising the steps of;

at the source, creating n shares of the source data according to apredetermined secret sharing scheme and sending the shares to the datanetwork, while encrypting the sent data using (n,k) secret sharing;

using a centralized network controller (such as network controller is acontroller for managing an SDN) or network management tools at thesender for dynamically managing a plurality of partially independentpaths, over which the shares are routed from the source to thedestination, such that the number of shares that pass the router at eachnode along each path does not exceed a threshold of k−1 shares. Optimalpaths are dynamically determined by the network controller/sender,according to the threshold and to theload/current-eavesdropping-coalition-risks on each router in the datanetwork.

The problem of finding paths may be reduced to the maximum flow problem(which may be solved for example, using the Dinitz's algorithm, or oneof a plurality of other existing maximum flow algorithms) by expandingthe original (directed or undirected) graph representing the datanetwork.

The number of unique paths that are required to apply the (n,k) secretsharing scheme on the network, may be varied by the controller inresponse to a coalition of two or more routers.

Whenever a coalition of routers is detected/suspected, the sender or thecontroller may be adapted to merge the nodes of the coalition and tofind a flow that fulfills the sharing scheme constraints.

The secret sharing scheme may be implemented on the network'sApplication Layer by:

receiving the data before it gets into the networking stack;

applying secret-sharing on the entire data;

establishing a connection for each route and sending the shares ondifferent sockets using TCP or UDP, depending on the required service.

The secret sharing scheme may be implemented on the network's TransportLayer by:

at the source, applying secret-sharing only on the packet's payload,while keeping the headers of the Transport Layer public, while allowingsome minor changes, like the length and the checksum;

at the source, creating n packets with the same headers of all layers;

at the destination, buffering k out of n shares and applying thesecret-sharing algorithm, to reconstruct the original data;

reconstructing the header of the Transport Layer and sends a singlepacket (out of the k shares) to the Transport Layer implementation ofthe destination.

The secret sharing scheme may be implemented on the Network Layer by:

at the source, applying secret-sharing on the payload and the headers ofthe Transport Layer, while keeping the headers of the Network Layerpublic, thereby creating n packets with the same headers of the DataLink and the Network Layers while allowing some minor changes, likelength, checksum and CRC).

at the destination, buffering k out of n shares and applyingsecret-sharing algorithm to construct the original data;

sending a single packet (out of the k shares) to the Transport Layerimplementation of the destination.

The secret sharing scheme may be implemented on the Data Link layer byapplying secret-sharing on the payload and the headers of the NetworkLayer and Transport Layer, while keeping the headers of the Data Linklayer public on the LAN or on a Virtual LAN (VLAN), while allowing someminor changes, like length and CRC).

The secret sharing scheme may be implemented on the Physical Layer byapplying secret-sharing on the payload and the headers of the Data LinkLayer, Network Layer and Transport Layer, while keeping all headersprivate.

The secret sharing scheme may be implemented to perform one sideidentification between a client and a server, without the need to use akey that is certified by a third party, by:

allowing the client to send a nonce via multiple channels to the serveraccording to the listing of the server in several self-verifiable publicdirectories; applying secret-sharing by the client;

the client receives the server's data from addresses mentioned in thepublic directory and sends the shares over different separated channels,such that each channel gets a share of the data and only by having allshares or a threshold of the shares, the data can be reconstructed;

the server gets the required number of shares and reconstructs the sentdata.

The secret sharing scheme may be implemented to perform double sideidentification between a client and a server, without the need to use akey that is certified by a third party, using one/two/three handshakeprotocols, by:

allowing the client to send its ID and a nonce, while each channel getsa share of the data, so that, only by having all or a threshold of theshares, the data can be reconstructed;

the server creates shares from the nonce, receives the client addressdata from the public directory and sends the shares over differentchannels;

the server sends its own information with the nonce it got from theclient through multiple channels to the client, such that each channelgets only a share of the data;

the client verifies the nonce and gets the server information;

the client verifies the nonce and sends an acknowledgement throughdifferent channels to multiple addresses of the server along with thenonce to the server; the server finalizes the authentication byreconstructing the acknowledgement, and starts a session using one ormore channels.

The present invention is further directed to a method for establishing afully private, information theoretically secure interconnection betweena source and a destination over a managed data network having at least aportion of a public infrastructure, comprising:

at the source, creating n shares of the source data according to apredetermined secret sharing scheme and sending the shares to the datanetwork, while encrypting the sent data using n−k secret sharing;

using a centralized network controller for dynamically managing aplurality of partially independent paths, over which the shares arerouted from the source to the destination, such that the number ofshares that pass the router at each node along each path does not exceeda threshold of k−1 shares. Optimal paths are dynamically determined bythe network controller, according to the threshold and to the load oneach router in the data network.

The secret sharing scheme may be hierarchical secret sharing, where atleast one secret share is further secret shared by an intermediatenetwork component, and gathered by one of the next components or by thedestination.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIGS. 1a and 1b illustrate an original undirected graph and itscorresponding expanded graph, respectively;

FIG. 2a illustrates an original directed graph G of a flow example;

FIG. 2b illustrates the resulting flow and the paths of the differentshares on the corresponding expanded graph of FIG. 2 a;

FIG. 3 (prior art) illustrates a conventional process for obtaining acertification from a CA;

FIG. 4a illustrates a process of one side authentication, using thesecret sharing scheme proposed by the present invention; and

FIG. 4b illustrates a process of double side authentication, using thesecret sharing scheme proposed by the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention proposes a novel alternative for establishinginformation theoretical secure and private interconnection, which isbased on multipath communication that is efficiently implementable bycurrent technology, cloud computing, point-of-presence, backup lines andinfrastructures (wired connection, phone, messaging systems, internet,wireless, satellite, etc.) together with social networks and theirsearchable directories (phone directory, Facebook, Twitter, Linked) forrobust authentication and avoidance of identity theft. The presentinvention uses a data separation scheme for establishing an informationtheoretically secure private channel in communication networks. In casewhen a service provider uses a cloud to extend its available services byusing virtualized servers on the cloud, the service provider mustguarantee the customers that the interconnections between datacenters isprivate, and therefore, these interconnection is transparent to anypotential customer. The proposed interconnection is informationtheoretic secured, in particular, there is no key that by revealing it,privacy will be compromised.

In one embodiment, the proposed solution uses secret sharing schemealong with different tunnels, to transfer the data while ensuringprivacy. Encryption with (n; k) secret sharing scheme (n≧k) is done bycreating n shares from the data, such that only by having at least kshares, the data can be decrypted, and any subset of less than k sharescannot be used to decrypt the data. The present invention proposes usinga secret sharing scheme (such as Shamir: “How to share a secret”, ACM 22(11), 1979) as a communication infrastructure for indefinitely securingdata in transit.

According to the proposed scheme, the source creates n shares from thedata and sends them over a data network to the destination throughseveral tunnels, such that no node (router) along a tunnel intercepts kor more shares. This way, only the destination that gets all the sharescan decrypt the data, resulting in a private channel between the sourceand the destination. When n>k, n−k shares can get lost, due tocongestion or even by malicious routers. The secret-sharing scheme canbe implemented in several communication layers for example, in theTransport Layer, where only the payload of each packet is shared or atthe Network Layer, where also the Transport layer headers are shared.This data network can be either unmanaged, such as the current IPnetwork with normal routing or managed (e.g., SDN).

If there are no different routes between the two edges, encapsulation isused (i.e., a special header which forces the packets of the shares topass via predetermined nodes) to create tunnels. These tunnels arecreated in different directions on the path from the source to thedestination, such that no router intercepts k or more shares.

The appliance/virtual-appliance required for implementing the proposeddata separation scheme can easily be integrated into any enterpriseenvironment and is compatible with any communication and/or securityinfrastructures. The appliance/virtual-appliance is installed inside theenterprise, before the data traffic leaves or enters the enterprise. Inorder to have multiple paths between the edges, the appliance (oranother routing device after it and inside the enterprise) must have atleast two interfaces, or routes to another entity along the path with atleast two interfaces, to form at least two separate routes between eachpair of sites. In any case, there is no effect on current traffic andconfiguration and the sharing process is transparent to the routersacross the paths.

The specific deployment locations of the appliance may vary, dependingon several constraints. On the sender side, typically the earliest pointwhere the secret sharing process can be implemented is after theimplementation of the upper layer in the networking stack.

The appliance may be installed before or after the existing VPN. Byinstalling it after the VPN on the sender side, it means that the VPNencrypted data is split into shares and reconstructed on the receiverside before sending it to the VPN. Switching locations is alsosupported, i.e., any share of the appliance/virtual-appliance passes tothe VPN to be encrypted.

Example 1: Unmanaged Network

If the data network is unmanaged (like in most cases), the separationbetween tunnels can be made by encapsulation of the shares' packetsaccording to a routing scheme that creates at least partiallyindependent routing paths from source to destination, along which nonode (router) along a tunnel intercepts k or more shares. This is doneby changing the headers of each share-carrying packet to a modifiedheader and deploying a plurality of Points of Presence (PoPs—e.g.,servers) in different locations (e.g., countries) over the network, andforcing the shares' carrying packets to pass through selected PoPs(which are nodes, as well). Each packet may be forced to pass a possibledifferent subset of selected PoPs. Alternatively or in addition, it ispossible to use public clouds that are anyway deployed over the network,as PoPs, by embedding a dedicated agent into many of them. The sharecarrying packets will be sent from the source to the destination, suchthat the modified header will determine the next intermediatedestination which will be the PoP or cloud agent that has been selectedwhile creating each modified header. Each agent will be able to receivean encapsulated packet (with the modified header), read its destination,encapsulate it by replacing its header with another modified headerwhich corresponds to the next intermediate destination (the next PoP orcloud agent) and send it over the data network to that nextintermediate. The modified header may be a part of the payload. Thisprocess is repeated until the last PoP or cloud agent sends the packetto the original destination. This way, shares of encrypted data arerouted in a controllable manner, thereby creating the required tunnelsthat force sufficient separation between segments of each path. In anycase, each dedicated agent determines only a segment until the nextintermediate destination along the path from source to destination.

This routing scheme is superior over the prior art solutions sinceunlike prior art, it does not require totally independent paths fromsource to destination. Using encapsulation and PoPs or cloud agents asrouting nodes, it is possible to route share carrying packets via manysegments, resulting from additional splitting of the paths betweenintermediate destinations. For example, if n=6 and k=4, it is possibleto send 3 packets via one segment and 3 via another segment. It ispossible that later some of the first group of 3 packets and the secondgroup will traverse the same node as long as their total number issmaller than 4. Thus, no particular share has an independent path, butstill the secrecy is preserved. Also, if one of the nodes of thesegments is congested or inactive, it is possible to split the packetdelivery to 3 segments, each of which carries 2 packets.

There are cases in which the network in unmanaged but there are morethan one VLANs between the source and the destination. In such a case,assuming these VLANs use different routers, it is possible to use theexisting VLANs as several paths between the source and the destination.

If the data network is unmanaged but has a known topology, say bynetwork management tools, it is possible to test the flow offline oronline at the sender side, in order to obtain the distribution of datathrough different nodes and deploy/redeploy the dedicated agents (andthereby to determine the PoPs or cloud agent) accordingly, to create theoptimal routing paths.

If the data network is unmanaged and has an unknown topology, it ispossible to use traceroute (a utility that records the route through theInternet between a source computer and a specified destinationcomputer), or similar tools such as TraceMAC (traceroute for MACaddresses)/Batal (B.A.T.M.A.N. advanced control and management tool), HPOpenView (a Hewlett Packard product family that consisted of network andsystems management products) or the Free Network Automatic TestingSystem (FreeNATS—is an open source network monitoring softwareapplication) in order to obtain the expected distribution of datathrough different nodes and verify, before sending the share carryingpackets, such that no node (router) along a path intercepts k or moreshares, regardless the nodes from which they arrive.

According to another embodiment, it is possible to perform dynamicallocation of nodes (dedicated agents or PoPs), through which the sharecarrying packets will pass, in order to obtain sufficient dataseparation. For example, 10 agents or PoPs may be deployed at differentlocations and the initial routing scheme resulting from using tracerouteindicated that 6 agents (out of 10) were selected to establish severalrouting paths with sufficient separation. Then, after sending the sharesaccording to the initial routing scheme (via the initially selectednodes), it is possible to periodically use traceroute to verify if thereare unexpected problems (e.g., congestion, delay or temporary inactiverouter) at one or more nodes along each routing paths. If no problematicnode is detected, packets will be sent according to the initial routingscheme. On the other hand, whenever a problematic node is detected, amodified routing scheme will be created dynamically using some othernodes that will be allocated to bypass the problematic node, usinganother combination of 6 agents or more (out of 10), and packets will besent according to the modified routing scheme. This process is repeated,until all packets arrive to their destination. This solution may alsoimprove performance, since the router at each node has predeterminedrouting priority (according to the source or destination of the packet).Therefore, if the share carrying packets are forced to pass viaintermediate nodes, some of these intermediate nodes may have improvedrouting priority. As a result, a proper selection of the intermediatenodes can improve the time it takes the packets to reach theirdestination. In addition, dynamic path selection may be used to avoidtracing the communication pattern, e.g., packet timing pattern, bysniffers that sniff a subset of the paths.

According to a further embodiment, in case the data network uses an IPv6protocol (Internet Protocol version 6, in which IP addresses are 128bits long) it is possible to use the inherent additional header of IPv6for creating tunnels between IPv6 nodes, where data between nodes can besent over IPv4 protocol links (Internet Protocol version 4, in which IPaddresses are 32 bits long). This tunneling implementation save theoverhead involved while performing encapsulation via adding a modifiedheader to the payload.

According to an additional embodiment, when it is required to hide theIP address of the destination of the forwarded data shares, the proposeddata sharing scheme may be used to encrypt the destination IP address,along with the payload data. This is done by creating n shares from theIP address of the destination (i.e., the header data) and sending theseshares via several different paths between pairs of neighboringintermediate nodes, using the proposed data sharing scheme, such thatthe header data can be decrypted at each intermediate nodes only byhaving at least k shares, and any subset of less than k shares cannot beused to decrypt the header data. This way, each intermediate node willcollect the shares of the destination, reconstruct the IP address of thedestination and add the header to the next intermediate node, until thedestination is reached. This additional splitting of the destination IPaddress (which is essentially similar to tunneling between source anddestination) will be made preferably in path segments with higherprobability for coalitions of eavesdroppers reducing the possibleidentification of related packets, and hiding the vicinity of thesource/destination from eavesdroppers, which contains much information.Splitting accompanied by secret sharing must be done while preservingthe hierarchy according to which each share has been re-split, such thatall re-split shares that are collected by an intermediate node will beof the same level (to avoid collision between shares resulting fromunequal numbers of re-splitting, which will require more effort to becombined). Each intermediate node can transmit data regarding thesplitting level in the hierarchy, to the next intermediate node.

In a similar way, the proposed data sharing scheme may be used toencrypt the source IP address, along with the payload data. This is doneby creating n shares from the IP address of the source and sending theseshares as part of the payload of the secret shared packet, using theproposed data sharing scheme, such that the real source IP (which issecret shared as part of the payload by the source) will be revealedonly by the destination. In this case, the first (or any/every)intermediate node along the path sets itself as the source, in order toforward the shares to the next intermediate node.

The proposed data sharing scheme can be enhanced by creating secretshared packets of different length by padding the after secret sharedpackets with random string of varying lengths, to avoid correlation ofpackets by a coalition of eavesdroppers. Also, delaying some of thesecret shared packets to avoid time correlation, and even sending somecorrupted secret shared packets that can be discarded by the destinationthat receives enough secret shares but can full the coalition ofeavesdroppers.

According to another embodiment, the proposed data sharing scheme may beused to encrypt data packets with restricted latency and deadlines (suchas of voice or video packets) that can be influenced and can be moresensitive to synchronization issues that maybe yielded from multiplesplitting to secret shares (at the sender) and gathering (at thereceiver). In this case, a one-time-pad (being a random bit string) iscreated in the background at the sender side and is then securely sentto the destination over several paths (using the proposed secret sharingscheme). As a result, only the destination can reconstruct thisone-time-pad, in order to be later used to decrypt the received (latencysensitive payload) data that will be sent using (bitwise, bit by bit,XOR, with) the common established one-time-pad. Once the destination hasthe one-time-pad, the sender performs a bitwise (bit by bit) XORoperation between the payload data and the random bit string (to obtainencryption of the payload data) and sends the resulting bits ofencrypted payload data over a single channel (just as it was originallytransmitted, with no splitting). Then, the payload data, encrypted bythe shared produced one-time-pad, is sent over a single path to thedestination, with no additional latency problems. This technique can beused for securely sending movies as well, since no extra latency orreliability problems are introduced, while sending the data from side toside over a single path. The shared one time pad can be also regarded asa shared key when one wants to turn to using computational basedschemes.

Example 2: Managed Network

In another embodiment, the method proposed by the present inventionsuggests using secret sharing in combination with a managed network,such as an SDN, to enable the secret sharing scheme to be managed by theSDN controller. The general idea of the proposed solution is to use SDNto enable the creation of several tunnels between each pair ofdatacenters that intercommunicate. The source uses a secret sharingtechnique to encrypt its data and create n shares. In order toreconstruct the data, the destination must have at least k shares out ofthe n shares that were sent by the sender. The present inventionproposes a method for creating these tunnels with the constraint thatonly less than k shares of the same information can reach a singlerouter. This way, a private and secure interconnection between thedatacenters is obtained. In order to ensure this privacy, n−k secretsharing is used to encrypt the data. The source creates n shares of itsdata and sends them to the network. The SDN controller manages the pathssuch that no k or more shares pass the same router. This way, theinterconnection between the datacenters is information theoreticallysecured, i.e. unless two or more routers share their data, the encrypteddata can never be revealed.

According to the proposed scheme, the problem of finding these paths canbe reduced to the maximum flow problem by expanding the original graph.By having a centralized controller or network management tools at thesender, it is possible to compute the flow on the network and determinea bound on the ratio n/k, which is the number of unique paths that arerequired to apply the n−k secret sharing scheme on the network. Once theflow and the values of n and k are obtained, the sender creates n sharesof each packet such that each flow is expanded to n flows where the flowID is the flow data along with the share index. This way, thecontroller, which gets the first packet of each flow (corresponding tothe new definition of flow), routes the shares to the correspondingpaths and the private channel between the datacenters/endpoints isestablished.

The SDN controller defines the route of each flow that occurs in thedata plane. The controller calculates a route for each flow, and adds anentry for that flow in each of the routers along the path. With allcomplex functions subsumed by the controller, routers simply manage flowtables whose entries can be populated only by the controller.Communication between the controller and the routers uses a standardizedprotocol and API. Most commonly, this interface is the OpenFlowspecification (“OpenFlow: Enabling innovation in campus networks”,SIGCOMM Comput. Commun. Rev., 38(2)69-74, March 2008). In an SDNarchitecture, each router forwards the first packet of a flow to the SDNcontroller, thereby enabling the controller to decide whether the flowshould be added to the router flow table. When a packet of a known flowis encountered, the router forwards it out the appropriate port based onthe flow table. The flow table may include some additional informationdictated by the controller. With the decoupling of the control and dataplanes, SDN enables applications and services to deal with a singleabstracted network device without concern for the details of how thedevice operates. Network services see a single API to the controller.Thus, it is possible to quickly create and deploy new applications tocoordinate network traffic flow to meet specific enterprise requirementsfor performance or security.

After creating the n shares, the sender adds an index i, 1≦i≦n to eachshare, this index becomes a part of the flow id and thus for eachoriginal flow, the controller handles n “first” packets of these ninitiated flows. Furthermore, each router may have more than one entrybut up to k−1 entries for each flow, where k is the threshold of thesecret sharing scheme. This index can be added either by adding thisfield into the matching fields structure in the SDN controller platformwhich causes a change also at the routers, or to use vendor extensionswhich allow different kinds of matching. By creating the paths based onthe maximum flow algorithm, it is possible to program the controller toroute the shares such that no router intercepts k or more shares. In thecurrent example, if in FIG. 2b gets the first 4 shares then theforwarding table of v_(5,2) may contain the entries at Table I.

TABLE I Forwarding Table of V5, 2. Flow Id Next Hop f₁ v_(7, 1) f₂v_(7, 1) f₃ v_(6, 1) f₄ v_(6, 1)

There is no limit on the number of packets that go through a singlerouter as long as it does not see k or more packets of the same flow.

A secret-sharing scheme is a method by which a dealer distributes nshares to parties such that only authorized subsets of at least kparties can reconstruct the secret. In this case, when one datacenterintends to communicate with another datacenter, it creates n shares ofits message and distributes these shares over the network. The SDNcontroller routes these shares to the target datacenter in a way that norouter on the way intercepts k or more shares. This way, a privatechannel between the datacenters is established. In this case, k can beequal to n if it is assumed that the channels are reliable and nodes donot omit or corrupt shares. Since only k shares are needed noreconstruct the secret, when n>k, approach similar to forward erasurecorrecting or error correcting, such as the Berlekamp Welch technique(presented in U.S. Pat. No. 4,633,470 where n is greater than k+2e towithstand e corruptions), can be used to overcome erasures and evencorruptions of at most n−k shares.

Example 3: Data Separation Using Main and Backup Channels

Almost any enterprise has a main channel and a backup channel toexchange data, these two channels are totally independent and separated(otherwise the backup channel will not be able to be a real replacementin case the main channel fails). In this case, since there is no mutualsegment along each path from source to destination, no node intercepts kor more shares.

Data Separation Problem

The problem of data separation between tunnels is examined as graphtheory problem. A graph G=(V, E) is given, with a source node s (whichhas only outgoing flow) and a sink node t (which has only incomingflow). Each node vεV has a determined non-negative capacity C_(v). Thegoal is to push as much flow as possible from s to t in the graph. Eachpath p_(i) has a flow f_(pi), the rule is that the sum of the flows ofall paths that each node intercepts cannot exceed its capacity,formally, for each node v,

Σp _(i) |vεp _(i) f _(pi) ≦C _(v).

Reduction to the Maximum Flow Problem

The problem can be reduced to the known maximum network flow problemwhere each edge e in E has an associated non-negative capacity C_(e),where for all non-edges it is implicitly assumed that the capacity is 0.In this problem, the goal is to push as much flow as possible from s tot in G, such that no edge can have flow exceeding its capacity, and forany vertex except s and t, the flow into the vertex must be equal to theflow out from the vertex.

The original graph, G, does not have to be directed. In order to reducethe problem to the maximum flow problem, each vertex v in G is expandedto a directed edge (v₁, v₂). The expansion process is presented atAlgorithm 1:

Algorithm 1: The Expansion Process Input: G=(V,E),s,t,k−1

for all uΣV|uj=s,t do

V=V¥{u}

V=V∪{u₁,u₂}E=E∪{(u₁,u₂)}c_((u) ₁ _(,u) ₂ ₎=c_(u)for all e=(s,v)εE do

E=¥{e} E=E∪{(s,v₁)}

c_((s,v) ₁ ₎=k−1for all e=(u, t)εE do

E=E¥{e} E=E↑{(u₂,t)}

c_((u) ₂ _(,t))=k−1for all e=(u,v)εE|uj=s,t AND vj=s,t do

E=E¥{e}

E=E∪{(u₂,v₁)}c_((u) ₂ _(,v) ₁ ₎=k−1E=E∪{(v₂,u₁)}c_((v) ₂ _(,u) ₁ ₎=k−1

FIG. 2a illustrates an original undirected graph G. FIG. 2b illustratesits corresponding expanded graph. The input of the algorithm is theoriginal undirected graph G, the source s and sink t and the threshold kof the secret sharing scheme. At the first step, a directed edge(v_(i1), v_(i2),) is added for each vertex v_(i), in G (except for s andt), for example, (v_(1,1), v_(1,2)) in FIG. 2b . The capacity of thisnew edge is the capacity Cv_(i) of the vertex v_(i). Then each edge (s,v_(i)) from the source is replaced by the directed edge (s, v_(i,1))i.e., edges (s, v_(i,1)) and (s, v_(2,1)) in v_(5,2),). Each edgedirected to the sink (v_(j), t) is replaced by (v_(j,2), t), i.e.,(v_(5,2), t) and (v_(6,2), t) in FIG. 2b , respectively. Then in case Gis undirected, for each other edge (v_(i), v_(j)) in G, two directededges, (v_(i,2), v_(j,1)) and (v_(j,2), v_(i,1)) are added, for example,(v_(1,2), v_(2,1)) and (v_(2,2), v_(1,1)). In order to eliminate thepossibility that edge sniffers will reveal the secret, the capacity ofthese edges is set to be k−1.

Since the capacity of the nodes in the original graph also representsk−1 edges, all the capacities of all edges are equal. If |V| is thenumber of vertices and |E| is the number of edges in G, the resulteddirected graph, Gt is a graph with (|V|−2)×2+2 vertices and up to(|E|−2)×2+2 edges. The expanded graph Gt is directed to force the pathsto include the edges of the expanded vertexes but the input graph can beeither directed or undirected. In case of a directed graph, a directededge (v₁, v₂) is still added for each vertex v, but for each otherdirected edge (v_(i), v_(j)), only the edge (v_(i,2), v_(j,1)) is added(and not (v_(j,2), v_(i,1)) as was done for an undirected G).

Firstly, the maximum flow problem will be defined. One of the mostefficient solutions for that problem has been proposed by “Dinitz′Algorithm: The Original Version and Even's Version”, (Theoreticalcomputer science”, pages 218-240, Springer-Verlag, Berlin, Heidelberg,2006). Dinitz's algorithm was selected since it is strongly polynomial.The algorithm uses shortest augmenting paths and its complexity isO(V²E), under a common assumption is that there are more links thanrouters. Alternatively, any of the plurality of known maximum flowalgorithms can be used, as well.

If G=(V, E) be a network with s, tεV being the source and the sink of G,respectively. The capacity of an edge is a mapping c:E→R⁺, denoted byc(u, v). It represents the maximum amount of flow that can pass throughan edge.

A flow is a mapping f: E→R+, denoted by f (u, v), subject to thefollowing two constraints:

-   1) f (u,v)≦c(u, v), for each (u, v)εE (capacity constraint: the flow    of an edge cannot exceed its capacity).-   2) Σ_(u:(u,v)εE) f (u,v)=Σ_(u:(v,u)εE f) (v, u), for each vεV\{s, t}    (conservation of flows: the sum of the flows entering a node must    equal the sum of the flows exiting a node, except for the source and    the sink nodes).

The value of flow is defined by |f|=Σv:(s,v)εE f (s, v), where s is thesource of G. It represents the amount of flow passing from the source tothe sink. The maximum flow problem is to maximize |f|, that is, to routeas much flow as possible from s to t.

Dinitz uses few definitions in his solution. The first is the residualcapacity; which is computed as c_(f)(u, v)=c(u,v)−f(u, v) and c_(f)(v,u)=f (u, v) for each (u, v)εE; The residual graph is the graphG_(f)=((V, E f), c_(f)|E_(f) s, t), where E_(f)={(u, v)εV×V: c_(f) (u,v)>0}. The level graph id defined by GL=(V, EL, c_(f)|EL, s, t), whereE_(L)={(u, v)εE_(f):dist(v)=dist(u)+1}. The last definition is dist(v),which is the length of the shortest path from s to v in G_(f). By usingthese definitions, Dinitz shows that the maximum flow problem can besolved in Θ(V²E). Dinitz approach is used to create the flow. Thisresulting flow defines the paths over which the shares will be sent.

The maximum flow problem is related to the minimum-cut problem. Theproblem of s−t minimum cut in a flow network is finding the minimumnumber of edges in the cut-set that creates a cut where the source andthe sink are in different subsets. The cut-set only consists of edgesgoing from the source's side to the sink's side. In other words, if theedges in the cut-set are removed, then flow form the source to the sinkis completely cut off. The cut-set value is the sum of the flowcapacities in the source-to-sink direction over all of the edges in thecut-set. The minimum cut problem is to find the cut-set that has theminimum cut value over all possible cuts in the network. For anynetwork, having a single source and a single sink, the maximum possibleflow from source to sink is equal to the minimum cut value for all cutsin the network. The proof stems from the fact that the maximum flowthrough a series of linked pipes equals the maximum flow in the smallestpipe in the series, i.e., the flow is limited by the bottleneck pipe.

FIG. 3a illustrates an original directed graph G of a flow example. Inorder to determine the minimum value of k, the s-t minimum cut iscalculated on the expanded graph. If the minimum cut-set contains tedges, then n/k has to be less than t. As seen, the cut-set in thisexample consists of two edges, (v_(4,1), v_(4,2)) and (v_(5,1),v_(5,2)). This implies that in this graph, n/2 must be lower than k. Inthis example, n=10 and k=7 were choose, i.e., each router can see atmost 6 shares and therefore this is the capacity on the (u1, u2) edges.FIG. 3b illustrates the resulting flow and the paths of the differentshares on its corresponding expanded graph.

The method proposed by the present invention considers the networkoverhead, as well. Each packet that is sent between the source and thedestination is split into n shares. Assuming that each share is sentwithin a packet, n packets are sent for a single packet of data.

If m packets of data should be sent from the source to the destination,n×m packets are sent. This might be considered impractical and a highvolume of data is sent in the network in general and in particularbetween the two nodes. Therefore, if this is the case, the proposedscheme can be used for exchanging keys for the use of standard VPNs.This way, the privacy of the keys is information theoretically securedand man-in-the-middle attacks are eliminated.

By using the (n, k) secret sharing scheme, it is possible evaluate apolynomial of degree k−1 at n points. This polynomial can be expressedas multiple linear operations and it requires O(n) multiplications. Inorder to recover the packet, the destination uses Lagrange interpolationpolynomial with complexity of O(k²).

The controller operates maximum once for each flow to construct themaximum flow algorithm on the network topology. In practice, it willcompute the algorithm only a few times for each couple of source anddestination since the network is typically undergo only limited andinfrequent dynamic changes. The computational complexity of thecontroller depends on the network size and it is O(V²E). In therealistic case where several controllers manage the network where eachcontroller has its own part of the network, this computation can be donein parallel, thus V and E are nodes and edges at each part of thenetwork.

The basic assumptions are that the nodes in the paths do not share theirdata and that the network is reliably managed by the controller, i.e.,the controller can be trusted. If this is not the case, either by amalicious controller or by an adversary that controls the controller,the controller can simply forward all shares to a single router toreveal the secret. In addition to the controller, it is also assumedthat the routers (the nodes in the graph notations) behave according tothe controller routes. If there is a coalition of two or more nodes, thecurrent solution might fail. Assume that, with probability p, nodes v4and v5 in FIG. 3a share their data, in that case, they should beconsidered as one node and therefore the cut-set of the correspondingexpanded graph contains only one edge, hence, there is no solution forany n or k. Thus, the probability that there is no solution for privatechannel is p. On the other hand, if, with probability p, nodes v2 and v3share their data, then after merging these two nodes, the cut-setcontains two edges, which implies that there are two paths from thesource to the sink, i.e., the n shares are now sent through two paths.

In the general case, if before merging two nodes in a coalition, thecut-set contains l edges, first the number of possibilities todistribute the n shares over the l paths with the constraint that eachedge in the cut-set intercepts at most k−1 shares should be calculated.This set of possibilities is called Λ. This is equivalent todistributing n balls in £ cells such that no cell contains more than k−1balls, or by rephrasing, all the possibilities to distribute n balls tothe l cells minus the possibilities that any of the cells contains k ormore balls. The number of possibilities in Λ is:

$\begin{matrix}{\begin{pmatrix}{n +  - 1} \\n\end{pmatrix} - { \times {\begin{pmatrix}{n - k + l - 1} \\{n - k}\end{pmatrix}.}}} & (1)\end{matrix}$

For simplicity, it is assumed that there are no cases in which two ormore cells contain k−1 balls, i.e., n<2k−2; this assumption isreasonable since at the end of this analysis, in order to maximize theprobability for a private interconnection, the best value for k is n andcertainly k>n/2+1. Out of the possibilities in Λ, those that fulfill theconstraint that the merged nodes see at most k−1 shares, or with theballs notations, the sum of balls in the two merged cells is less thanor equal to k−1 should be found. If it is the sum of balls in the mergedcells, then there are 1-2 more cells that each of which can contain upto k−1 balls, thus, the lower bound t_(lb) of t is

Max{n−(£−2)(k−1),0},  (2)

For each possible value of t, the number of possibilities ofdistributing t balls in the two merged cells times the number ofpossibilities to distribute the other n−t balls in the other £−2 cellsmust be calculated. Formally

$\begin{matrix}{\sum_{t_{lb} \leq t \leq {k - 1}}{\begin{pmatrix}{t + 1} \\t\end{pmatrix} \times {\begin{pmatrix}{n - t +  - 3} \\{n - t}\end{pmatrix}.}}} & (3)\end{matrix}$

Therefore the probability for a private interconnect in the general caseis given by:

$\begin{matrix}{{p \times \frac{\sum_{t_{lb} \leq t \leq {k - 1}}{\left( {t + 1} \right) \times \begin{pmatrix}{n - t +  - 3} \\{n - t}\end{pmatrix}}}{\begin{pmatrix}{n +  - 1} \\n\end{pmatrix} - { \times \begin{pmatrix}{n - k + l - 1} \\{n - k}\end{pmatrix}}}} + \left( {1 - p} \right)} & (4)\end{matrix}$

By choosing n=k and large n, this probability tends to 1. For example,if n=k=10 and l=3, then t_(lb)=1 and the probability to get a privateinterconnection is given by:

${{p \times \frac{\sum_{1 \leq t \leq 9}{\left( {t + 1} \right) \times \begin{pmatrix}{10 - t} \\{10 - t}\end{pmatrix}}}{\begin{pmatrix}12 \\10\end{pmatrix} - {3 \times \begin{pmatrix}2 \\0\end{pmatrix}}}} + \left( {1 - p} \right)} = {{{p \times \frac{\sum_{1 \leq t \leq 9}\left( {t + 1} \right)}{63}} + \left( {1 - p} \right)} = {{{p \times {54/66}} + \left( {1 - p} \right)} = {1 - {0.182\; p}}}}$

For n=k=20, the probability becomes 1−0.0833p. If the sender knows aboutthe possibility of a specific coalition and the probability to find aflow given that coalition is positive, it can first merge the nodes ofthe coalition and then find a flow that fulfills the sharing schemeconstraints. The above analysis was done for a single coalition of twonodes, in case there are more nodes in the coalition or anothercoalition, the same process can be done recursively.

At mentioned above, the time computation of the secret sharing schemedepends on n and k. Therefore, when there is full trust on the routers,n and k should be relatively low. In order to increase the probabilityof a private channel, in case there is some positive probability for acoalition in the network, the source may choose larger n and k, even inthe price of compromising the algorithm efficiency.

Implementation on OSI Layers

According to another embodiment, the proposed secret sharing scheme maybe implemented on different layers of the Open Systems Interconnection(OSI) model. This allows a system to communicate over differentcommunication layer that perfectly secure the data in transit over acommunication link.

Implementation on the Application Layer (which Handles the Communicationwith the User):

In this implementation, the data to be shared are the application layerpackets, before splitting the data into packets. The proposed secretsharing process on the source receives the data before it gets into thenetworking stack implementation. At the first step, the process appliesthe secret-sharing algorithm on the entire data. At the next step, itestablishes a connection for each route and sends the shares on thedifferent sockets (endpoints in a communication flow). In this case, theprocess can use either Transmission Control Protocol (TCP) or UserDatagram Protocol (UDP—a communications protocol that offers a limitedamount of service when messages are exchanged between computers in anetwork that uses the Internet Protocol), depending on the requiredservice. The receiver should maintain several sockets to get differentshares, this time after the networking stack is done with the packets.The process reconstructs the original data at the application.

When the packets traverse the network, there is no way to identify thatthe payload contains split data. This process is transparent to the DataLink layer, the Network layer and the Transport layer implementation onboth the sender and the receiver sides.

Implementation on the Transport Layer (which Handles the Data ExchangeBetween Parties and Reliability):

In this implementation, the data to be shared is only the payload, whilekeeping the headers of the Transport layer public. First, the process onthe source gets the packet before it leaves. Then, it applies thesecret-sharing algorithm on the payload, while creating n packets withthe same headers of all layers (Data Link layer, the Network layer andthe Transport layer). Since the routers on the way of the packetstraversing the network do not process the payload at any time, theproposed secret sharing process is transparent to them.

The proposed secret sharing process on the destination gets the packetswhen they enter the local network (before they reach the destination onthe Transport Layer implementation), first the secret sharing processbuffers k out of n shares and applies the secret-sharing algorithm, toreconstruct the original data. Then the secret sharing process adds theheaders of the Transport Layer and sends a single packet (out of the kshares) to the Transport Layer implementation of the destination. Thissecret sharing process is also transparent to the Transport layerimplementation on both the sender and the receiver sides. Theimplementation on the Transport Layer does not interfere with any devicethat inspects the packet headers at all levels, such as a firewall or aconventional VPN. In case where a device such as an Intrusion DetectionSystem (IDS) is part of the route (that examines the packet payload),the IDS should be located before splitting into shares on the senderside and after it, on the receiver side (again, in the same place wherea VPN is located).

Implementation on the Network Layer (which Handles Routing and DataTransfer Between Sides):

In this implementation, the data to be shared is the packets of theTransport Layer, i.e., the payload and the headers of the TransportLayer, while keeping the headers of the Network Layer public. Theproposed secret sharing process on the source gets the packet before itleaves, and applies the secret-sharing algorithm on the payload and theheaders of the Transport Layer. The process creates n packets with thesame headers of Data Link and the Network Layers.

When the packets traverse the network, since the routers on the way donot process the headers of the Transport Layer, the process istransparent to them. The process on the destination gets the packetswhen they enter the local network (again, before they reach thedestination in the Transport Layer implementation). It buffers k out ofn shares and applies the secret-sharing algorithm, to construct theoriginal data. Here, the data already contains the headers of theTransport Layer. Then it sends a single packet (out of the k shares) tothe Transport Layer implementation of the destination. The proposedsecret sharing process is also transparent to the Transport Layerimplementation, both at the sender and the receiver sides.

The implementation on the Network Layer is made right after the OSfinishes the implementation of the Network layer and on the transportlayer, and also interferes devices that inspect the headers of thetransport layer, such as a firewall. In this case, the splitting processshould be after the firewall or it should bypass the firewall, exactlyas it happens today when a VPN and a firewall listen to the same port.

Implementation on the Data Link Layer (which Handles Point to Point DataTransfer in Spite of Noise and Distortions):

In this implementation, the data to be shared is the Network Layer'spackets, i.e., the payload and the headers of the Network Layer andTransport. Layer, while keeping the headers of the Data Link layerpublic.

There are two architectures to implement the proposed secret sharingprocess on the Data Link layer: The first architecture is on the LAN,and the other is on a Virtual LAN (VLAN).

When implemented on the LAN, the network should be in a graph structure,rather than tree structure, namely, there are two or more paths forconnecting between host A and host B. In order to find the multiplepaths, it is possible to execute the proposed flow algorithm in the LAN.Then, after splitting the data, the source sends the shares through morethan one switch to the destination.

When implemented on a VLAN, there is a protocol that encapsulates theheaders of the Network Layer, for example Multiprotocol Label Switching(MPLS—a mechanism that directs data from one network node to the nextnode, based on short path labels rather than long network addresses).The routing in the VLAN is done through several switches by the DataLink layer protocol (sometimes is considered as layer 2.5). Thisprotocol creates tunnels in the Network Layer, so using the NetworkLayer, the source and destination in the VLAN are in the same LAN. Theproposed secret sharing process can be applied by creating multipletunnels between the source and the destination.

Implementation on the Physical Layer (which Handles Signal Transmission,Voltages and Connections)

In this implementation, the data to be shared is the Data Link packets,i.e., the payload and the headers of the Data Link Layer, Network Layerand Transport Layer, while keeping all headers private. This can be doneby separating the physical bandwidth, for example, by splitting lightwaves and sending the shares at the different waves.

In additionally to the above constraints, it is possible to implementthe proposed secret sharing process anywhere at the source and thedestination with the following additional limitations:

At the sender side, for each level, the earliest point where the processcan be implemented is after the implementation of the above layer in thenetworking stack. For example, the Network Layer implementation can beimplemented right after the OS completes the implementation of thetransmission layer in the networking stack. In any case, it can be rightbefore the packet leaves the network. With the same constraints for thereceiver, it can be the first step when the packets enter the network orjust before the above layer implementation, in the above example, itshould be right before the implementation of the transmission layer inthe networking stack.

In case there are devices such as VPN, Intrusion Detection System (IDS—adevice or application that analyzes whole packets, both header andpayload, looking for known events) or a firewall, the Application Layerand Transport Layer layers implementation does not interfere any devicethat examines the packet headers at all levels such as firewall or VPN.In case a device such as IDS (that examines the packet's payload) is onthe way, the IDS should be before the split into shares at the senderside and after it, at the receiver side (again, at the same place wherea VPN is located).

The Physical layer, Data Link layer and Network Layer implementationincludes also devices that examine Transport Layer and Network Layerheaders, such as a firewall. In this case, the splitting process shouldbe after the firewall or it should bypass the firewall, exactly ashappens today when the VPN and the firewall are installed on the sameport.

According to another embodiment, it is possible to employ the proposedsecret sharing scheme, or a random string sharing scheme, to performidentification between a client and a server, without the need to use akey that is certified by a third party. Today, identification (toauthenticate two parties) is done by having a public key certified by aCertification Authority (CA). Each entity has two keys, a public key anda private key. The public key is used to decrypt data by the other partyand the private key is used to decrypt it. For authentication purposes,data that was encrypted by a private key, can be decrypted by a publickey. The conventional process for obtaining a certification from a CA ona public key is illustrated in FIG. 1. At the first step, the CA 10receives from one party a public key 11 along with the party'sidentifying data 12. The CA 10 signs the public key 11 using its privatekey 13 and issues a certificate 14 for that public key 11. The browseror the other party already possesses the public key of the CA andconsequently can verify the signature, trust the certificate and thepublic key in it. Since the first party uses a public key that the CAcertifies, a fake first party can only use the same public key. Sincethe fake first party does not know the corresponding private key, itcannot create the signature needed to verify its authenticity.

For example, if a server requires that a client will send some privatedata (e.g., a password), it needs to authenticate itself to the client.Normally, the server does that by using a service of one of the CAs(such as Verisign, Reston, Va., U.S.A.). The CA identifies the serverand uses its private key to sign the server's identification and publickey. By having the public key certified by a CA, the server isauthenticated to the client. The client uses the public key of the CA toreveal the server public key. There are two main problems with thisauthentication process, one is the need to trust a CA and the other isthe strength of the encryption. Today, anyone (benign or possiblymalicious entity) can establish a CA and in practice, this is thesituation in many cases. The browser does alert the client if it gets acertification from unknown CA but the typical client would simply pressthe “OK” button to continue. This is a major vulnerability that can besolved using the proposed secret sharing scheme. Furthermore, in manycases the strength of the identification depends on some password thatthe client chooses. As was proven many times, in many of the cases,these passwords are easy to guess.

By using the secret sharing scheme proposed by the present invention,such a guessing will become much harder. The new identification processproposed by the present invention does not require using anycertificates or certificate authorities. Instead, it creates severalseparated channels (tunnels) between communicating parties, along withsome of the public information of entities in the Internet. In addition,in order to identify using the secret sharing scheme of the presentinvention, a user must have at least two (logical or preferably alsoactual) networking paths (and/or applications) where the user can getdata in, for example, email, Facebook, LinkedIn, SMS, etc. (thiscollection is sometimes called a “public trust”, where publiclyavailable identity information is used for authentication, as aredundancy for a trusted authority). The main idea of the newidentification process is that one side sends some data through these(at least logically) separated channels to the other side and by havingall (or some threshold of) the pieces of the data, the other side canconstruct the data, find the details on the entity that proposes theconnection and verify it.

The new identification process proposed by the present invention canhave one side authentication or both sides authentication.

One Side Authentication

If it is only required to authenticate a server to a client, the oneside authentication process will include the following steps (which areillustrated in FIG. 5a ):

At the first step, the client takes the following actions to send somemessage or/and nonce (a random number generated for a specific use, suchas session authentication) together with own identification informationvia multiple channels to the server according to the listing of theserver in several (self-verifiable) public directories (e.g., a phonedirectory, email, Facebook, Twitter LinkedIn searches, governmentagencies, newspaper, IP address, etc.). A self-verifiable publicdirectory is a public directory which essentially can withstandidentity-theft attempts. Each entity in a self-verifiable publicdirectory can verify its own details, so as to make sure that the datarepresenting these details is up-to-date and has not corrupted by a 3rdparty. Otherwise, the self-verifiable public directory will notify thepublic directory's moderator that the data is not up-to-date. The datais secret shared by the client. Next step the client received theserver's data from the addresses mentioned in public directory and sendsthe shares over different separated channels, such that each channelgets a share of the data and only by having all (or a threshold of the)shares, the data can be reconstructed. The data may include all thefound listing information so that the server may identify its own wronglisting in some of the directories, as a result of non-updated listingor phishing. At the next step, the server gets the required number ofshares and reconstructs the client's nonce. At that step the serverreceives the message of the client, and the client has succeeded sendingthe message to the server in a secure fashion, in this “one-wayauthenticated” version the server does not send the identifier of theclient over multiple channels.

Double Sides Authentication

If it is required that both sides will authenticate themselves, theclient side will perform the steps described before (for one sideauthentication). In turn, the double side authentication process willfurther include the following steps (which are illustrated in FIG. 5b ):

At the first step, the client sends its ID and some nonce (a numbergenerated for a specific use, such as session authentication) viamultiple public accounts of the server over multiple channels, such thateach channel gets a share of the data and only by having all (or athreshold of the) shares, the data can be reconstructed. The data mayinclude all the found listing information so that the server mayidentify its own wrong listing in some of the directories, as a resultof non-updated listing or phishing. Again, each channel gets a share ofthe data, so that, only by having all (or a threshold of the) shares,the data can be reconstructed. The server creates shares from the noncereceived, possibly augmenting the nonce with a new nonce, and its own IDinformation, searches the client data in the public directories andsends the shares over different channels. At the next step, the clientverifies the nonce and gets the server information. At the next step,the client sends an acknowledgement through the different channels tomultiple addresses of the server along with the nonce (or with acombination, such as bitwise XOR of the two nonce, when the serverreplies with a new nonce) to the server. At the next step, the serverfinalizes the authentication by reconstructing the acknowledgement, and,in case also confidentiality is required, starts a session usingmultiple channels (using the agreed IP addresses that are part of theidentification information), possibly using the nonce as a (first)common shared secret or a seed for creating sequence numbers for theshares. One/two/three way handshake procedures based on using publicdirectories and secret shares sent by multi-path communication areessentially the core of the proposed authentication schemes.

It should be indicated that using a public trust may be sometimesvulnerable to phishing and identity stealing attempts. Suchvulnerabilities may be overcome by using a self-authentication process,during which an entity (e.g., a bank) periodically performsself-searches of its own public contact details in all publicdirectories (in the same way that other entities search these publicdirectories), to ensure that there is no identity theft (by comparingthe search results to its authentic public contact details). Once anidentity detects a mismatch in a public directory (i.e., a stolen orfake identity), it issues an alert to that public directory to blockaccess to it. The frequency of performing these self-searches isnormally increased if the risk level increases.

The secret sharing scheme proposed by the present invention can overcomesome levels of identity theft, by using error correction algorithms. Inthis case, even if an intruder cracked one of the public directories(e.g., LinkedIn) and sends fake identity data, it will be still possibleto reconstruct the nonce by using error correction algorithms, such asthe Berlekamp Welch technique. This may be done by finding a polynomialin which one or more points (up to a threshold e) are incorrect, but isstill revocable by the redundancy implied by n>k.

According to another embodiment, instead of using a secret sharing theproposed solution may use other data separation schemes. For example, itis possible to select a sequence of bits (a coding sequence) with thesame length as of the data sequence and decode and encode the datasequence by performing a logic operation (such as XOR) between the twosequences. Then, the resulting (encoded) bit sequence and the codingsequence are sent to the destination via separate tunnels. This way,only the destination (which receives the full sequences will be able todecode the data sequence and reveal the data by performing another XORoperation. Such a solution also keeps the size of the sent packets thesame as the original packet's size. According to another example, it ispossible to encode the data sequence using Reed-Solomon code and sendsegments of the coded sequence via to the destination via separatetunnels. This way, only the destination (which receives the fullsequences will be able to decode the data sequence and reveal the databy decoding it with the same Reed-Solomon code.

The solution proposed by the present invention may be used to protectselected systems in an enterprise, such as email s or other types ofdata, rather than protecting the entire data traffic that is sent from,or received by, the enterprise.

The above examples and description have of course been provided only forthe purpose of illustration, and are not intended to limit the inventionin any way. As will be appreciated by the skilled person, the inventioncan be carried out in a great variety of ways, employing more than onetechnique from those described above, all without exceeding the scope ofthe invention.

1. A method for establishing a fully private, information theoreticallysecure interconnection between a source and a destination over anunmanaged data network having at least a portion of a publicinfrastructure, comprising: a) at said source, creating n shares of thesource data according to a predetermined secret sharing scheme andsending said shares to said data network, while encrypting the sent datausing (n,k) secret sharing; b) deploying a plurality of intermediatingnodes in different locations over said network, thereby creating aplurality of fully and/or partially independent paths in differentdirections on the path from said source to said destination, and withsufficient data separation; and c) sending said shares over saidplurality of fully and/or partially independent paths while forcingshares' carrying packets to pass through selected intermediate nodes,such that no router at any intermediating nodes intercepts k or moreshares.
 2. A method according to claim 1, wherein the intermediatingnodes include one or more of the following: Points of Presence (PoPs);Computational clouds having a dedicated for forcing shares' carryingpackets to pass through selected intermediate nodes, according to adesired routing scheme; Backup channels and paths.
 3. A method accordingto claim 1, wherein the portion of the public infrastructure includesalternative paths supplied by the same/different network/Internetproviders.
 4. A method according to claim 1, wherein the separationbetween tunnels belonging to fully and/or partially independent paths ismade by encapsulation of the shares' packets according to a routingscheme that creates at least partially independent routing paths fromsource to destination, such that no node along a tunnel intercepts k ormore shares.
 5. A method according to claim 4, wherein duringencapsulation, the headers of each share-carrying packet is changed to amodified header, for forcing the shares' carrying packets to passthrough selected nodes.
 6. A method according to claim 5, wherein eachpacket is forced to pass a possible different subset of selected nodes.7. A method according to claim 1, further comprising using public cloudsdeployed over the network as nodes, by embedding a dedicated agent intoa plurality of them, such that the modified header will determine thenext intermediate destination which will be the node that has beenelected while creating each modified header.
 8. A method according toclaim 7, wherein the modified header is a part of the payload.
 9. Amethod according to claim 1, wherein whenever the data network has aknown topology, the flow is tested offline, to obtain the distributionof data through different nodes and deploy the dedicated agentsaccordingly, to create the optimal routing paths.
 10. A method accordingto claim 1, wherein whenever the data network has unknown topology apath/topology recovery tools are used to obtain the expecteddistribution of data through different nodes and verify, before sendingthe share carrying packets.
 11. A method according to claim 10, whereinthe path/topology recovery tools are selected from the group of:HP-OpenView; Freenats; Traceroute; TraceMAC; Batctl.
 12. A methodaccording to claim 1, wherein sufficient data separation is obtained bydynamically allocating nodes, through which the share carrying packetswill pass.
 13. A method according to claim 1, wherein the inherentadditional header of IPv6 is used for creating tunnels between IPv6nodes, where data between nodes is sent over IPv4 protocol links.
 14. Amethod according to claim 1, further comprising encrypting thedestination IP address, along with the payload data, by: creating nshares from the IP address of the destination; sending said shares viaseveral different paths between pairs of neighboring intermediate nodes,such that the header data is decrypted at each intermediate nodes onlyby having at least k shares, and any subset of less than k shares cannotbe used to decrypt the header data.
 15. A method according to claim 1,further comprising creating secret shared packets of different length bypadding the after secret shared packets with random string of varyinglengths, to avoid correlation of packets by a coalition ofeavesdroppers.
 16. A method according to claim 1, further comprisingdelaying some of the secret shared packets to avoid time correlation.17. A method according to claim 1, further comprising encrypting datapackets with long payloads by creating a one-time-pad in the backgroundat the sender side; sending the created a one-time-pad to thedestination over several paths; performing a bitwise XOR operationbetween the payload data and the bit string of said common one-time-pad;and sending the resulting bits of encrypted payload data over possibly asingle channel.
 18. A method for establishing a fully private,information theoretically secure interconnection between a source and adestination over a managed data network having at least a portion of apublic infrastructure, comprising: a) at said source, creating n sharesof the source data according to a predetermined secret sharing schemeand sending said shares to said data network, while encrypting the sentdata using (n,k) secret sharing; b) using a centralized networkcontroller or network management tools at the sender for dynamicallymanaging a plurality of partially independent paths, over which saidshares are routed from said source to said destination, such that thenumber of shares that pass the router at each node along each path doesnot exceed a threshold of k−1 shares, wherein optimal paths aredynamically determined by said network controller/sender, according tosaid threshold and to the load/current-eavesdropping-coalition-risks oneach router in said data network.
 19. A method according to claim 15,wherein the problem of finding paths is reduced to the maximum flowproblem by expanding the original graph representing the data network.20. A method according to claim 15, wherein the network controller is acontroller for managing an SDN.
 21. A method according to claim 15,wherein the number of unique paths that are required to apply the (n,k)secret sharing scheme on the network, is varied by the controller inresponse to a coalition of two or more routers.
 22. A method accordingto claim 16, wherein the original graph is directed or undirected.
 23. Amethod according to claim 16, wherein the maximum flow problem is solvedusing the Dinitz's algorithm, or one of a plurality of other existingmaximum flow algorithms.
 24. A method according to claim 17, whereinwhenever a coalition of routers is detected/suspected, the sender or thecontroller is adapted to merge the nodes of the coalition and to find aflow that fulfills the sharing scheme constraints.
 25. A methodaccording to claim 15, wherein the secret sharing scheme is implementedon the network's Application Layer by: a) receiving the data before itgets into the networking stack; b) applying secret-sharing on the entiredata; c) establishing a connection for each route and sending the shareson different sockets using TCP or UDP, depending on the requiredservice.
 26. A method according to claim 15, wherein the secret sharingscheme is implemented on the network's Transport Layer by: a) at thesource, applying secret-sharing only on the packet's payload, whilekeeping the headers of the Transport Layer public, while allowing someminor changes, like the length and the checksum; b) at the source,creating n packets with the same headers of all layers; c) at thedestination, buffering k out of n shares and applying the secret-sharingalgorithm, to reconstruct the original data; d) reconstructing theheader of the Transport Layer and sends a single packet (out of the kshares) to the Transport Layer implementation of the destination.
 27. Amethod according to claim 1, wherein the secret sharing scheme isimplemented on the Network Layer by: a) at the source, applyingsecret-sharing on the payload and the headers of the Transport Layer,while keeping the headers of the Network Layer public, thereby creatingn packets with the same headers of the Data Link and the Network Layerswhile allowing some minor changes, like length, checksum and CRC). b) atthe destination, buffering k out of n shares and applying secret-sharingalgorithm to construct the original data; c) sending a single packet(out of the k shares) to the Transport Layer implementation of thedestination.
 28. A method according to claim 1, wherein the secretsharing scheme is implemented on the Data Link layer by applyingsecret-sharing on the payload and the headers of the Network Layer andTransport Layer, while keeping the headers of the Data Link layer publicon the LAN or on a Virtual LAN (VLAN), while allowing some minorchanges, like length and CRC).
 29. A method according to claim 1,wherein the secret sharing scheme is implemented on the Physical Layerby applying secret-sharing on the payload and the headers of the DataLink Layer, Network Layer and Transport Layer, while keeping all headersprivate.
 30. A method according to claim 1, wherein the secret sharingscheme is implemented to perform one side identification between aclient and a server, without the need to use a key that is certified bya third party, by: a) allowing the client to send a nonce via multiplechannels to the server according to the listing of the server in severalself-verifiable public directories; b) applying secret-sharing by theclient; c) the client receives the server's data from the addressesmentioned in public directory and sends the shares over differentseparated channels, such that each channel gets a share of the data andonly by having all shares or a threshold of the shares, the data can bereconstructed; d) the server gets the required number of shares andreconstructs the sent data.
 31. A method according to claim 1, whereinthe secret sharing scheme is implemented to perform double sideidentification between a client and a server, without the need to use akey that is certified by a third party using one/two/three handshakeprotocols, by: a) allowing the client to send its ID and a nonce, whileeach channel gets a share of the data, so that, only by having all or athreshold of the shares, the data can be reconstructed; b) the servercreates shares from the nonce, receives the client address data from thepublic directory and sends the shares over different channels; c) theserver sends its own information with the nonce it got from the clientthrough multiple channels to the client, such that each channel getsonly a share of the data; d) the client verifies the nonce and gets theserver information; e) the client verifies the nonce and sends anacknowledgement through the different channels to multiple addresses ofthe server along with the nonce to the server; f) the server finalizesthe authentication by reconstructing the acknowledgement, and starts asession using one or more of the channels.
 32. A method for establishinga fully private, information theoretically secure interconnectionbetween a source and a destination over a managed data network having atleast a portion of a public infrastructure, comprising: a) at saidsource, creating n shares of the source data according to apredetermined secret sharing scheme and sending said shares to said datanetwork, while encrypting the sent data using n−k secret sharing; b)using a centralized network controller for dynamically managing aplurality of partially independent paths, over which said shares arerouted from said source to said destination, such that the number ofshares that pass the router at each node along each path does not exceeda threshold of k−1 shares, wherein optimal paths are dynamicallydetermined by said network controller, according to said threshold andto the load on each router in said data network.
 33. A method accordingto claim 1, wherein the secret sharing scheme is hierarchical secretsharing, where at least one secret share is further secret shared by anintermediate network component, and gathered by one of the nextcomponents or by the destination.